Cargo Stuff form

Operations Cargo Cargo Lots Cargo Lots view Actions Stuff Cargo Stuff form

From the Actions menu in the following Inspectors:

Cargo Lots view Cargo Lot Inspector

Bills of Lading view Bill of Lading Inspector Items tab Bill of Lading Item form Cargo Lots tab

Units view Unit Inspector Cargo Lots tab

Vessel Visits view Vessel Visit Inspector Cargo Lots tab

Train Visits view Train Inspector Cargo on Board tab

Railcar Visits Railcar Visits view Railcar Visit Inspector Cargo on Board tab

In N4, you can stuff cargo units in the yard into a unit in the yard. You can use the Cargo Stuff form to stuff the selected cargo units into the specified container. You can stuff multiple cargo items from different yard locations or from a truck into a container. The cargo lots may be associated with the same or different bills of lading.

Prerequisites for stuffing a cargo lot into an empty storage unit.

A vessel visit in the Working phase.
An Export bill of lading (on page 1).
A bill of lading item (on page 1) for bulk or non-bulk cargo.
A cargo unit in the yard (a B-Bulk unit must exist in the Units view for the cargo lot).

To stuff a cargo unit into an empty storage unit:

In the Cargo Lots view (on page 1), select the cargo lot(s) that you want to stuff into a unit.

The cargo lot must have a cargo unit associated with it and the position of the cargo unit can be in the yard or truck. You cannot select a default cargo lot to perform the stuff action.

Select Actions Stuff.
In the Cargo Stuff form:

Optionally, in the Service Order Nbr field, enter the ID of the service order for the stuff action.

The specified service order must exist in N4. To add a new service order, use the Actions Create Service Order (on page 1) option.

In the Container field, enter the Unit Nbr of the unit into which you want to stuff the selected cargo lot(s).

If the commodity associated with the cargo lot has temperature requirements, you can stuff the selected cargo lot only into a reefer container.

In the Quantity field, edit the prompted value if you do not want to stuff the entire cargo lot quantity in the unit.

If you select multiple cargo lots in the list view, N4 does not display the Quantity field. The entire quantity of all the selected cargo lots is stuffed into the selected container.

Select the Direct Stuff check box to perform a stuff operation directly from a truck into a container.

Select the Truck Complete check box to move the truck to the next stage after the stuff operation.
Click Save.

When you successfully stuff the entire quantity of a cargo lot into the specified container, N4:

In the Units view:

Retires the B-Bulk unit and sets the Cargo Quantity = 0.
Records the CARGO_STUFF event for the B-Bulk unit. If a cargo work order is available for the cargo item, N4 records this event against the cargo work order and also updates the Qty Completed and Status columns for the cargo work order item.

You can use the Unit Inspector History, Events tab or the Cargo Lot Inspector (on page 1) History, Events tab to view the details of the event.

GC_STUFF event for the cargo lot and bill of lading. You can use the History, Events tab in the Cargo Lot Inspector (on page 1) and Bill of Lading Inspector (on page 1) to view the event details..
If the Freight Kind of the selected container unit is Empty, N4 retires the unit and creates a new unit with Freight Kind = FCL.

If you select multiple cargo lots in the Cargo Lots view and the cargo lots are associated with multiple bills of lading, the Freight Kind of the new unit is LCL. If the selected cargo lots are associated with the same bill of lading, the Freight Kind of the new unit is FCL.

If the Freight Kind of the selected unit is FCL or LCL, N4 does not retire the unit.
Adds the cargo lot Quantity to the Cargo Quantity of the container unit.
Records the UNIT_STUFF event for the container unit.

For the Cargo Stuff action, N4 records a CARGO_STUFF event each time you stuff a partial or full quantity to a unit. However, it records the UNIT_STUFF action only once when you stuff the first cargo lot into the unit.

In the Cargo Lots view:

Sets the Lot Type of the cargo lot as Container.
Associates the new unit with the cargo lot in the Unit Nbr field.
Updates the position of the cargo lot to match the Position of the new FCL container in the Yard.
If you specified a service order in the Cargo Stuff form, N4 also updates the status of the service order after successfully completing the stuff action.

Holds/Permissions for Strip and Stuff actions

N4 provides a Groovy hook with the Strip and Stuff actions for a cargo lot to enable you to control which holds/permission are transferred as part of the operation.

The following code sample represents the Groovy plug-in that you can edit to specify which holds/permission are transferred as part of the Strip and Stuff actions. This example transfers the CARGO_UNLOAD hold as part of the Strip or Stuff action:

import java.util.ArrayList;

import java.util.Collection;

import java.util.List;

import com.navis.apex.business.model.GroovyInjectionBase;

import com.navis.cargo.business.model.CargoLot;

import com.navis.inventory.business.units.Unit;

import com.navis.services.business.rules.Flag;

import com.navis.services.business.rules.FlagType;

class CustomHoldTypeListForTransferGroovyImpl extends GroovyInjectionBase {

public List<String> getHoldTypeList(Unit inFromUnit, Unit inToUnit) {

List<String> returnHoldTypeIds = new ArrayList();

log("From Unit:"+inFromUnit.getUnitId()) ;

log("To Unit:"+inToUnit.getUnitId()) ;

Collection flags = FlagType.findActiveFlagsOnEntity(inFromUnit);

for (Object flagObj : flags) {

Flag flag = (Flag) flagObj;

//You can add the list of all holds/permissions that you want to

//move as part of the Strip and Stuff actions.

if (flag.getFlagFlagType().getId().equals("CARGO_UNLOAD")){

returnHoldTypeIds.add(flag.getFlagFlagType().getId()) ;

}

return returnHoldTypeIds;

}

If the selected cargo lot has other holds/permissions associated with it, N4 does not transfer those as part of the Strip and Stuff actions. It transfers only the holds/permissions specified in the Groovy plug-in.

The Groovy class name and method signature must match exactly with that specified in the example above.

You can use this Groovy plug-in to transfer different holds for the Strip and the Stuff actions, if required. N4 uses the inFromUnit and inToUnit variables to determine the Freight Kind of the units. If the inFromUnit represents a containerized unit and inToUnit represents a break-bulk unit, then it is the Strip action. If the condition is reversed, it is the Stuff action.